Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479eea74251d26c7995a36b2a9d24fbd78269d5578cfbd49f8ed83d81770eb52

Tx prefix hash: a02bbc8fd9331334d69260fe4f48037f7e75d2db326686beaa85fea6611fb7cc
Tx public key: d4db8ee8a068bd1a20724ef9faef7f6bba8d75bc7399ab83834ab4cab6f44c03
Timestamp: 1715110633 Timestamp [UCT]: 2024-05-07 19:37:13 Age [y:d:h:m:s]: 00:337:00:44:50
Block: 1017025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240899 RingCT/type: yes/0
Extra: 01d4db8ee8a068bd1a20724ef9faef7f6bba8d75bc7399ab83834ab4cab6f44c030211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d844ca1447449b9e2fc6f258ed3de4c6b9d3a1471bdb106f98d16ea2615cdf5 0.600000000000 1480780 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": 1017035, "vin": [ { "gen": { "height": 1017025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d844ca1447449b9e2fc6f258ed3de4c6b9d3a1471bdb106f98d16ea2615cdf5" } } ], "extra": [ 1, 212, 219, 142, 232, 160, 104, 189, 26, 32, 114, 78, 249, 250, 239, 127, 107, 186, 141, 117, 188, 115, 153, 171, 131, 131, 74, 180, 202, 182, 244, 76, 3, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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