Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db93b5f5466001b486aaeb4269701db973a910c50b9dd89d35bc7f66d32ca835

Tx prefix hash: 82ea3f3eef37f25459f607f9220fb6b7e1d50e4a559947f7a93e840aaac42a37
Tx public key: b875a5c3e8589a2951e66f9760ab1ffa8e645156da00e8a6490d2a3f2f856989
Timestamp: 1733737118 Timestamp [UCT]: 2024-12-09 09:38:38 Age [y:d:h:m:s]: 00:142:07:33:55
Block: 1171344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101514 RingCT/type: yes/0
Extra: 01b875a5c3e8589a2951e66f9760ab1ffa8e645156da00e8a6490d2a3f2f856989021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61560505fefbda16a14f8228b3510115e83b685e15207f05448f0fb0f9de7d0d 0.600000000000 1657087 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": 1171354, "vin": [ { "gen": { "height": 1171344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61560505fefbda16a14f8228b3510115e83b685e15207f05448f0fb0f9de7d0d" } } ], "extra": [ 1, 184, 117, 165, 195, 232, 88, 154, 41, 81, 230, 111, 151, 96, 171, 31, 250, 142, 100, 81, 86, 218, 0, 232, 166, 73, 13, 42, 63, 47, 133, 105, 137, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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