Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 986753f8c659644affa1267e71b264be6f7c083f3235fd22bcb822caa7bcc3d4

Tx prefix hash: 55da6619a739c6469ce7d566efd2ddd171ae04ec7ed53a6d41b9509d6e53ef3f
Tx public key: 4cda3e95bff16b5e736611e9482c0a5c25c678d1133fbdfd44f3c146d16c09ca
Timestamp: 1735425224 Timestamp [UCT]: 2024-12-28 22:33:44 Age [y:d:h:m:s]: 00:092:15:14:53
Block: 1185308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65989 RingCT/type: yes/0
Extra: 014cda3e95bff16b5e736611e9482c0a5c25c678d1133fbdfd44f3c146d16c09ca0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b35845a4e32dbfcd04e421180e59081952a32ae1d483e1bbefa6496fe200ac8 0.600000000000 1671775 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1185318, "vin": [ { "gen": { "height": 1185308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b35845a4e32dbfcd04e421180e59081952a32ae1d483e1bbefa6496fe200ac8" } } ], "extra": [ 1, 76, 218, 62, 149, 191, 241, 107, 94, 115, 102, 17, 233, 72, 44, 10, 92, 37, 198, 120, 209, 19, 63, 189, 253, 68, 243, 193, 70, 209, 108, 9, 202, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8