Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc6dd28f53ec88013f46c3736d63ec4b9654469a01cfa08156e0623d180bf7e5

Tx prefix hash: 6f90278628b0df9975b0f40d7da8a44d3ab178953dff8815a16b566c40874360
Tx public key: 52dd85e5ff640b7c719b1a8a3383c408a16486cf7d4e55e70096d801e41682de
Timestamp: 1733007619 Timestamp [UCT]: 2024-11-30 23:00:19 Age [y:d:h:m:s]: 00:131:20:26:00
Block: 1165297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94046 RingCT/type: yes/0
Extra: 0152dd85e5ff640b7c719b1a8a3383c408a16486cf7d4e55e70096d801e41682de0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26046a6d8ff9d6c2a18fb2b2c085cb29fe8d68bc080287e88dc4dd8fbbd02f23 0.600000000000 1650972 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": 1165307, "vin": [ { "gen": { "height": 1165297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26046a6d8ff9d6c2a18fb2b2c085cb29fe8d68bc080287e88dc4dd8fbbd02f23" } } ], "extra": [ 1, 82, 221, 133, 229, 255, 100, 11, 124, 113, 155, 26, 138, 51, 131, 196, 8, 161, 100, 134, 207, 125, 78, 85, 231, 0, 150, 216, 1, 228, 22, 130, 222, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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