Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7a95f6df42cc4e050d1a8fa9c2c7d17456c01dc6c6e0c5dd5aaf1500bdbaa28

Tx prefix hash: 115445e9853610a67b22bd6fd8dd4ee79fc0bad3f9b26c106e6dd7b9de8f63dd
Tx public key: ee3ce885771c51da095cd72593e33b0cd3699a9df7c5c66726222b4d3e4639fe
Timestamp: 1728305070 Timestamp [UCT]: 2024-10-07 12:44:30 Age [y:d:h:m:s]: 01:034:04:37:15
Block: 1126411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282811 RingCT/type: yes/0
Extra: 01ee3ce885771c51da095cd72593e33b0cd3699a9df7c5c66726222b4d3e4639fe02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb1a691b6524b83193e426283db148af80be88da106004b41de9d1840935317c 0.600000000000 1609202 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": 1126421, "vin": [ { "gen": { "height": 1126411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb1a691b6524b83193e426283db148af80be88da106004b41de9d1840935317c" } } ], "extra": [ 1, 238, 60, 232, 133, 119, 28, 81, 218, 9, 92, 215, 37, 147, 227, 59, 12, 211, 105, 154, 157, 247, 197, 198, 103, 38, 34, 43, 77, 62, 70, 57, 254, 2, 17, 0, 0, 0, 1, 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