Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd632520d46400bb7bcfba7e95e2a3d8c9680d780e4f2dcbb4a741cf53f73a3c

Tx prefix hash: 8b0e1f1cac3b2119dce57953a04a5f2f075fefc312ae643eaf945ff2f8cd2e71
Tx public key: bc4c9d72a7c914e34e59a8e244e239682463ebada4cb3399fc7d9b6fc33eb280
Timestamp: 1728811681 Timestamp [UCT]: 2024-10-13 09:28:01 Age [y:d:h:m:s]: 00:069:15:59:51
Block: 1130613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49807 RingCT/type: yes/0
Extra: 01bc4c9d72a7c914e34e59a8e244e239682463ebada4cb3399fc7d9b6fc33eb28002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d32ada9fd02a2ce625bd3a44b9ce05e37eceac32b95f721bbe3b355d934d422 0.600000000000 1613490 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": 1130623, "vin": [ { "gen": { "height": 1130613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d32ada9fd02a2ce625bd3a44b9ce05e37eceac32b95f721bbe3b355d934d422" } } ], "extra": [ 1, 188, 76, 157, 114, 167, 201, 20, 227, 78, 89, 168, 226, 68, 226, 57, 104, 36, 99, 235, 173, 164, 203, 51, 153, 252, 125, 155, 111, 195, 62, 178, 128, 2, 17, 0, 0, 0, 5, 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