Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3187fd6720f346b39d569b862cee23b3249bc677cd50087bb345d6e27a29ceb

Tx prefix hash: d5ddc05b8ae5eab19dde57ab084744dc4a2986115244e730947f8d27cf21e948
Tx public key: ebd4f0ab37f30580eb46c188f155e4e29bd4a6f1d7ac6b2198d1809e987e2f18
Timestamp: 1702069950 Timestamp [UCT]: 2023-12-08 21:12:30 Age [y:d:h:m:s]: 01:335:05:58:31
Block: 908906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498467 RingCT/type: yes/0
Extra: 01ebd4f0ab37f30580eb46c188f155e4e29bd4a6f1d7ac6b2198d1809e987e2f1802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca9ab1e12aa1b813aa425d59997c67b8633f6e039c0719f632f71ffe9832a229 0.600000000000 1365967 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": 908916, "vin": [ { "gen": { "height": 908906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca9ab1e12aa1b813aa425d59997c67b8633f6e039c0719f632f71ffe9832a229" } } ], "extra": [ 1, 235, 212, 240, 171, 55, 243, 5, 128, 235, 70, 193, 136, 241, 85, 228, 226, 155, 212, 166, 241, 215, 172, 107, 33, 152, 209, 128, 158, 152, 126, 47, 24, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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