Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb5e6b4e4ab9109e210dfaa302ee642967f7da61fd5cc83cc7c7e592021a3d1

Tx prefix hash: cbdd165bca96f99fe4b9fa8cd7082a95e903a709959a565fbca461ca4805c2d8
Tx public key: 8d451ddca3111bf2a7e86a6d13fe3e45da580ec16ff989cdacb6ba075cf89bee
Timestamp: 1609270098 Timestamp [UCT]: 2020-12-29 19:28:18 Age [y:d:h:m:s]: 04:307:01:40:51
Block: 171604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1230581 RingCT/type: yes/0
Extra: 018d451ddca3111bf2a7e86a6d13fe3e45da580ec16ff989cdacb6ba075cf89bee02110000031e57f0ba47000000000000000000

1 output(s) for total of 165.731619882000 dcy

stealth address amount amount idx
00: cf1028612a9d722443426e65a35c9337f3d00e1743de0490b36902b117411699 165.731619882000 323463 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": 171614, "vin": [ { "gen": { "height": 171604 } } ], "vout": [ { "amount": 165731619882, "target": { "key": "cf1028612a9d722443426e65a35c9337f3d00e1743de0490b36902b117411699" } } ], "extra": [ 1, 141, 69, 29, 220, 163, 17, 27, 242, 167, 232, 106, 109, 19, 254, 62, 69, 218, 88, 14, 193, 111, 249, 137, 205, 172, 182, 186, 7, 92, 248, 155, 238, 2, 17, 0, 0, 3, 30, 87, 240, 186, 71, 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