Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c81e480f682f515716892580af8575289ff880cfd6fa0f12f1a73a875e46c39

Tx prefix hash: d44cc01aef9d5d18166376a266932c344ff3e6731a40f46ca8b10537ee020842
Tx public key: 453a3f17f0f5c2b3eb5c1d75cae87d995802648b239a2e04af12611004ffb00c
Timestamp: 1692849310 Timestamp [UCT]: 2023-08-24 03:55:10 Age [y:d:h:m:s]: 01:084:04:03:55
Block: 832625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321483 RingCT/type: yes/0
Extra: 01453a3f17f0f5c2b3eb5c1d75cae87d995802648b239a2e04af12611004ffb00c02110000000875e3f0e9000000000000000000

1 output(s) for total of 1.069468058000 dcy

stealth address amount amount idx
00: a2cdeeac636c3362d0b8ad321ea602b10e0559e70a0599ab94435a0e1392d56e 1.069468058000 1285073 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": 832635, "vin": [ { "gen": { "height": 832625 } } ], "vout": [ { "amount": 1069468058, "target": { "key": "a2cdeeac636c3362d0b8ad321ea602b10e0559e70a0599ab94435a0e1392d56e" } } ], "extra": [ 1, 69, 58, 63, 23, 240, 245, 194, 179, 235, 92, 29, 117, 202, 232, 125, 153, 88, 2, 100, 139, 35, 154, 46, 4, 175, 18, 97, 16, 4, 255, 176, 12, 2, 17, 0, 0, 0, 8, 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