Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944091a4e5592833328c3c36f07d1337a71e9c7a4f79d9c20db821703216f853

Tx prefix hash: a0f26485dbf9dda22bb4aa80d778211bcc5a49c70d5e47da9fbe73d2d8322aa2
Tx public key: eb772d243256fc8fe7a58eebedc503fe44830f0c4c21c4ce18e8e98e687a755f
Timestamp: 1729007593 Timestamp [UCT]: 2024-10-15 15:53:13 Age [y:d:h:m:s]: 00:001:02:54:38
Block: 1132239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 797 RingCT/type: yes/0
Extra: 01eb772d243256fc8fe7a58eebedc503fe44830f0c4c21c4ce18e8e98e687a755f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd9e487b21bc41a0834d85c9e6c06c48f6dc0b262cb46bd965e22f5156f42cf2 0.600000000000 1615152 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": 1132249, "vin": [ { "gen": { "height": 1132239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd9e487b21bc41a0834d85c9e6c06c48f6dc0b262cb46bd965e22f5156f42cf2" } } ], "extra": [ 1, 235, 119, 45, 36, 50, 86, 252, 143, 231, 165, 142, 235, 237, 197, 3, 254, 68, 131, 15, 12, 76, 33, 196, 206, 24, 232, 233, 142, 104, 122, 117, 95, 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