Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 390ab74d864de906706ed1fc26b4ba59c27a5d07cf77c44d6cbb777d0b38dc34

Tx prefix hash: fdaa7fd5837f5c47c99a04d821008d6370a168bf09641a2c6d9a97362242dc81
Tx public key: 0c5492f01da615684b5824dde2bc7c15c1078b221b16e52876719c8e7a4ea7f3
Timestamp: 1702012338 Timestamp [UCT]: 2023-12-08 05:12:18 Age [y:d:h:m:s]: 01:100:22:41:53
Block: 908427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333303 RingCT/type: yes/0
Extra: 010c5492f01da615684b5824dde2bc7c15c1078b221b16e52876719c8e7a4ea7f3021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3143177c3ce0e4d987fe12b749b30b8e302cf1417763c782445fde9a66be6bb8 0.600000000000 1365460 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": 908437, "vin": [ { "gen": { "height": 908427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3143177c3ce0e4d987fe12b749b30b8e302cf1417763c782445fde9a66be6bb8" } } ], "extra": [ 1, 12, 84, 146, 240, 29, 166, 21, 104, 75, 88, 36, 221, 226, 188, 124, 21, 193, 7, 139, 34, 27, 22, 229, 40, 118, 113, 156, 142, 122, 78, 167, 243, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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