Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970b69aca23e48081a0248849152a69d24dec4d54041734d95fd23e1caf2fc1c

Tx prefix hash: b6f50102bc6e0d877e9c699b2630d747ec6c3e16acbbc085691d8d09e48d1a59
Tx public key: 6ba1ff3601433ef065ea109b75d77c6ab6c52155229879e30fc2f4a962ed07ae
Timestamp: 1617066066 Timestamp [UCT]: 2021-03-30 01:01:06 Age [y:d:h:m:s]: 03:316:18:46:13
Block: 229359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 985649 RingCT/type: yes/0
Extra: 016ba1ff3601433ef065ea109b75d77c6ab6c52155229879e30fc2f4a962ed07ae0211000000333634f08d000000000000000000

1 output(s) for total of 106.671031678000 dcy

stealth address amount amount idx
00: 898bc119d634f60d2d5a04a7dc04937fb61f02298139710ac1b6a4dd96533e0c 106.671031678000 475871 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": 229369, "vin": [ { "gen": { "height": 229359 } } ], "vout": [ { "amount": 106671031678, "target": { "key": "898bc119d634f60d2d5a04a7dc04937fb61f02298139710ac1b6a4dd96533e0c" } } ], "extra": [ 1, 107, 161, 255, 54, 1, 67, 62, 240, 101, 234, 16, 155, 117, 215, 124, 106, 182, 197, 33, 85, 34, 152, 121, 227, 15, 194, 244, 169, 98, 237, 7, 174, 2, 17, 0, 0, 0, 51, 54, 52, 240, 141, 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