Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dd1a34fd9855977f01fe46a8491f45f8666237144c59dad3d15f5f746d7a741

Tx prefix hash: 9e1b7bc6877977905df87790882a281eb1c60f8ecf00d48c56af7b00d9dc4844
Tx public key: 244c8980a8cae5e158f6a66af266ff04dc206c0819208486b5c759d93bd63c3d
Timestamp: 1731054883 Timestamp [UCT]: 2024-11-08 08:34:43 Age [y:d:h:m:s]: 00:016:02:12:58
Block: 1149122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11511 RingCT/type: yes/0
Extra: 01244c8980a8cae5e158f6a66af266ff04dc206c0819208486b5c759d93bd63c3d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3f044ad217d0dd586ddb77a8ed0d0b4cc0ee668d745fd400bd5248900cfa5b3 0.600000000000 1634127 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": 1149132, "vin": [ { "gen": { "height": 1149122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3f044ad217d0dd586ddb77a8ed0d0b4cc0ee668d745fd400bd5248900cfa5b3" } } ], "extra": [ 1, 36, 76, 137, 128, 168, 202, 229, 225, 88, 246, 166, 106, 242, 102, 255, 4, 220, 32, 108, 8, 25, 32, 132, 134, 181, 199, 89, 217, 59, 214, 60, 61, 2, 17, 0, 0, 0, 2, 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