Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d0491d358210afe2ff6f982abe61a945e9d7f23458b8337e302b796007435a8

Tx prefix hash: faaa8ecb7a294fbfb1f012432f24ebc925c55fb1443ba6e046e7c51982250209
Tx public key: 053d8ab121d7f60e98c8fbe25dafb5ba13327196a4435ea5e482ff524f9a82a4
Timestamp: 1727353595 Timestamp [UCT]: 2024-09-26 12:26:35 Age [y:d:h:m:s]: 00:059:01:19:48
Block: 1118521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42206 RingCT/type: yes/0
Extra: 01053d8ab121d7f60e98c8fbe25dafb5ba13327196a4435ea5e482ff524f9a82a4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94c71fdcdea79b90425c8f72d58b6bd1ce8df732789b27409a556fb2d099fb3d 0.600000000000 1599742 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": 1118531, "vin": [ { "gen": { "height": 1118521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94c71fdcdea79b90425c8f72d58b6bd1ce8df732789b27409a556fb2d099fb3d" } } ], "extra": [ 1, 5, 61, 138, 177, 33, 215, 246, 14, 152, 200, 251, 226, 93, 175, 181, 186, 19, 50, 113, 150, 164, 67, 94, 165, 228, 130, 255, 82, 79, 154, 130, 164, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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