Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 550f7cdbce9b427b075120f816e5ef47ad6cafd99f774ec51ccea69af1bf52b2

Tx prefix hash: dd285ea305ac3f6715860929d3770c208fc9aca86d293288386b1f2298fc6da5
Tx public key: 2fb88906cd362c0f2b0304969ade4f6b1b70317aae70af6dcb61be177b0963e6
Timestamp: 1719156357 Timestamp [UCT]: 2024-06-23 15:25:57 Age [y:d:h:m:s]: 00:328:02:06:11
Block: 1050542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234492 RingCT/type: yes/0
Extra: 012fb88906cd362c0f2b0304969ade4f6b1b70317aae70af6dcb61be177b0963e602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57a2847ff1b6ecf9b9e33ac7900615f73f90221961a3f4fd89ad5aa6733ae77c 0.600000000000 1520717 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": 1050552, "vin": [ { "gen": { "height": 1050542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57a2847ff1b6ecf9b9e33ac7900615f73f90221961a3f4fd89ad5aa6733ae77c" } } ], "extra": [ 1, 47, 184, 137, 6, 205, 54, 44, 15, 43, 3, 4, 150, 154, 222, 79, 107, 27, 112, 49, 122, 174, 112, 175, 109, 203, 97, 190, 23, 123, 9, 99, 230, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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