Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c8c69ae3ccbaf5b6337962abb90ecd65dc9c545c4d2b6a14d170b2fbf4cb4f7

Tx prefix hash: 766c0a002217558ae17bae796c8635cd5aa1826682916e6b1296b11ebf109ce6
Tx public key: c8637a1927dcb0d231b1af3ad10e3ddbec3354184b4ebe7199e832e599828954
Timestamp: 1585419484 Timestamp [UCT]: 2020-03-28 18:18:04 Age [y:d:h:m:s]: 04:279:06:05:30
Block: 89133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098370 RingCT/type: yes/0
Extra: 01c8637a1927dcb0d231b1af3ad10e3ddbec3354184b4ebe7199e832e5998289540211000000048a2ee0d9000000000000000000

1 output(s) for total of 310.953750016000 dcy

stealth address amount amount idx
00: 7e77d7474eb8d7cb7fb0b3902e5ffa8e630c07de5abe5f7f3fe6867b7f5e0e65 310.953750016000 160017 of 0

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": 89143, "vin": [ { "gen": { "height": 89133 } } ], "vout": [ { "amount": 310953750016, "target": { "key": "7e77d7474eb8d7cb7fb0b3902e5ffa8e630c07de5abe5f7f3fe6867b7f5e0e65" } } ], "extra": [ 1, 200, 99, 122, 25, 39, 220, 176, 210, 49, 177, 175, 58, 209, 14, 61, 219, 236, 51, 84, 24, 75, 78, 190, 113, 153, 232, 50, 229, 153, 130, 137, 84, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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