Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601f44ff9b5abac6d42f1fde9cc04a50b6367d0f72447354b3a22e2e35b2feb5

Tx prefix hash: e884e56cef9f99b9d7879ff0c489a64b2cef901abbf837db47a675ed580089c7
Tx public key: 595e7721d9b20b984a2f6bb466d33df8df09caa5febfda90c56a824f75991ea6
Timestamp: 1714317315 Timestamp [UCT]: 2024-04-28 15:15:15 Age [y:d:h:m:s]: 01:186:07:59:56
Block: 1010431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391819 RingCT/type: yes/0
Extra: 01595e7721d9b20b984a2f6bb466d33df8df09caa5febfda90c56a824f75991ea60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4eaabba71f19c818d6338ac0602c7bb360cc3469ac81d4d153e1f2a0a7fd056 0.600000000000 1472387 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": 1010441, "vin": [ { "gen": { "height": 1010431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4eaabba71f19c818d6338ac0602c7bb360cc3469ac81d4d153e1f2a0a7fd056" } } ], "extra": [ 1, 89, 94, 119, 33, 217, 178, 11, 152, 74, 47, 107, 180, 102, 211, 61, 248, 223, 9, 202, 165, 254, 191, 218, 144, 197, 106, 130, 79, 117, 153, 30, 166, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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