Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3ee7262fef256e4eab753f4704573c118b32dadeb2b4021e1d04f8e38a2742

Tx prefix hash: 155397d9b711f44169c84a3b25088f77702c026af00feaa61a526b7d8d6cab68
Tx public key: bbebb2d7be512df5397f85f74f8a1e75d83fc90184901a7906f802d002b800a5
Timestamp: 1704166622 Timestamp [UCT]: 2024-01-02 03:37:02 Age [y:d:h:m:s]: 01:018:02:59:28
Block: 926280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274257 RingCT/type: yes/0
Extra: 01bbebb2d7be512df5397f85f74f8a1e75d83fc90184901a7906f802d002b800a5021100000002ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feac81ff709500846c5bb47bc526b59c0e018a6b4f8c08485f7a38eb309aa234 0.600000000000 1384058 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": 926290, "vin": [ { "gen": { "height": 926280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feac81ff709500846c5bb47bc526b59c0e018a6b4f8c08485f7a38eb309aa234" } } ], "extra": [ 1, 187, 235, 178, 215, 190, 81, 45, 245, 57, 127, 133, 247, 79, 138, 30, 117, 216, 63, 201, 1, 132, 144, 26, 121, 6, 248, 2, 208, 2, 184, 0, 165, 2, 17, 0, 0, 0, 2, 172, 50, 141, 17, 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