Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfbd66d63ebfaf2101fe5a202b915295b9b4f67dabf2c30197921dfae08af2e0

Tx prefix hash: cb1376a651922fe030a36baeff8e0466d82a4e43f7fddd357a357bd51a819f86
Tx public key: 7d45a32c6fcd4105944a976e5cfec53685f7831dd1a815e28e45b0a892823d3e
Timestamp: 1710739139 Timestamp [UCT]: 2024-03-18 05:18:59 Age [y:d:h:m:s]: 00:251:13:44:37
Block: 980797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180084 RingCT/type: yes/0
Extra: 017d45a32c6fcd4105944a976e5cfec53685f7831dd1a815e28e45b0a892823d3e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 315eb7a9d897d067a3e6cabd1d96cfb34c215a18710e860d4e655bfe827ff758 0.600000000000 1440878 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": 980807, "vin": [ { "gen": { "height": 980797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "315eb7a9d897d067a3e6cabd1d96cfb34c215a18710e860d4e655bfe827ff758" } } ], "extra": [ 1, 125, 69, 163, 44, 111, 205, 65, 5, 148, 74, 151, 110, 92, 254, 197, 54, 133, 247, 131, 29, 209, 168, 21, 226, 142, 69, 176, 168, 146, 130, 61, 62, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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