Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f61f724c856a64e1917455b57b37261888882d99e46038fab6c49a3026df60b

Tx prefix hash: a9e2c3f9423f0bab8d2af7e69f6eb830cd82bf5f3cfcc9191272aef08963b120
Tx public key: a88270e7e5edf6fcd5d06c3e9bc3d92030b2bf2a9002af634ba045b1ef2e8a9e
Timestamp: 1727757806 Timestamp [UCT]: 2024-10-01 04:43:26 Age [y:d:h:m:s]: 00:054:11:21:28
Block: 1121871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38925 RingCT/type: yes/0
Extra: 01a88270e7e5edf6fcd5d06c3e9bc3d92030b2bf2a9002af634ba045b1ef2e8a9e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5d84e909dd580e9f9c6b826d898d989321c87f25e813a13bcf5cc440edad4c4 0.600000000000 1604228 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": 1121881, "vin": [ { "gen": { "height": 1121871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5d84e909dd580e9f9c6b826d898d989321c87f25e813a13bcf5cc440edad4c4" } } ], "extra": [ 1, 168, 130, 112, 231, 229, 237, 246, 252, 213, 208, 108, 62, 155, 195, 217, 32, 48, 178, 191, 42, 144, 2, 175, 99, 75, 160, 69, 177, 239, 46, 138, 158, 2, 17, 0, 0, 0, 3, 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