Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee25a03ab339b45b068055a0defab90a483310c0a054e172c0bbecf7c46befc9

Tx prefix hash: 814edbafd9a791a2b44a12fff96a1dfddd6e0e12a50b7a79a5e7828bfae89dd4
Tx public key: 4a9c40804b4e8abc9af93cfd985c9a1d04ebb2d0b48f78fed436cc99de4fe5df
Timestamp: 1705250907 Timestamp [UCT]: 2024-01-14 16:48:27 Age [y:d:h:m:s]: 01:130:16:22:42
Block: 935272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354534 RingCT/type: yes/0
Extra: 014a9c40804b4e8abc9af93cfd985c9a1d04ebb2d0b48f78fed436cc99de4fe5df0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bb354b3d6c1d26c1b7688d0c5bb7ad436b5a04ab7587a59c2edcd0eabd45589 0.600000000000 1393288 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": 935282, "vin": [ { "gen": { "height": 935272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bb354b3d6c1d26c1b7688d0c5bb7ad436b5a04ab7587a59c2edcd0eabd45589" } } ], "extra": [ 1, 74, 156, 64, 128, 75, 78, 138, 188, 154, 249, 60, 253, 152, 92, 154, 29, 4, 235, 178, 208, 180, 143, 120, 254, 212, 54, 204, 153, 222, 79, 229, 223, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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