Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e775fefee7a0c19f65973803ecf4935a0743ff59f80497b5478885ff4529d72c

Tx prefix hash: dbb1e7917b329d066eb7d1ab3cffb74f62fb7ea35f34592309e091934c61d5b0
Tx public key: 6f2d8944dd8108b0f8d4f53ec3b24dfa59b1e5a983b9004dacbafc6e1771b595
Timestamp: 1685953371 Timestamp [UCT]: 2023-06-05 08:22:51 Age [y:d:h:m:s]: 02:155:06:34:14
Block: 775543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 630737 RingCT/type: yes/0
Extra: 016f2d8944dd8108b0f8d4f53ec3b24dfa59b1e5a983b9004dacbafc6e1771b595021100000003faf35c9c000000000000000000

1 output(s) for total of 1.653119556000 dcy

stealth address amount amount idx
00: d25d0b214d496cecea8e41616001e914c77f54ccf23b9a46e0f344410d079d8b 1.653119556000 1225060 of 0

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": 775553, "vin": [ { "gen": { "height": 775543 } } ], "vout": [ { "amount": 1653119556, "target": { "key": "d25d0b214d496cecea8e41616001e914c77f54ccf23b9a46e0f344410d079d8b" } } ], "extra": [ 1, 111, 45, 137, 68, 221, 129, 8, 176, 248, 212, 245, 62, 195, 178, 77, 250, 89, 177, 229, 169, 131, 185, 0, 77, 172, 186, 252, 110, 23, 113, 181, 149, 2, 17, 0, 0, 0, 3, 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