Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f34055db4f75bfb64d564b4e8251a88e7268a2bda252a738ce691904c10ca5d

Tx prefix hash: 4c01fb326f6b30cd00e9ae4df119ee67c8926dbd8d1256d831fd56ac98c171ed
Tx public key: 1ed4fffc853a58740bd223e91a206792ec69b86d4fb0f4740a6389146815cd7e
Timestamp: 1720478394 Timestamp [UCT]: 2024-07-08 22:39:54 Age [y:d:h:m:s]: 01:123:12:17:47
Block: 1061531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346789 RingCT/type: yes/0
Extra: 011ed4fffc853a58740bd223e91a206792ec69b86d4fb0f4740a6389146815cd7e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc46d3a6b987ff53b82c7fed58b5bc5b3b9ec7118a890ce85eae5c6d8b3b54f2 0.600000000000 1532022 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": 1061541, "vin": [ { "gen": { "height": 1061531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc46d3a6b987ff53b82c7fed58b5bc5b3b9ec7118a890ce85eae5c6d8b3b54f2" } } ], "extra": [ 1, 30, 212, 255, 252, 133, 58, 88, 116, 11, 210, 35, 233, 26, 32, 103, 146, 236, 105, 184, 109, 79, 176, 244, 116, 10, 99, 137, 20, 104, 21, 205, 126, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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