Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d29b1ec041ec42474f55f1a198cd81e281d12f60f3d5afbc48d390161ac3dfd

Tx prefix hash: b0e02db6dc170a13be5e2f182b327585a2bb2374129916ed1b7aa4a01dff703f
Tx public key: e81ccbb38dfaf85afd61c84ba6d7bc3605278954e23c8b590c2e47dd5223de13
Timestamp: 1706037389 Timestamp [UCT]: 2024-01-23 19:16:29 Age [y:d:h:m:s]: 01:141:15:08:02
Block: 941773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362309 RingCT/type: yes/0
Extra: 01e81ccbb38dfaf85afd61c84ba6d7bc3605278954e23c8b590c2e47dd5223de1302110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e07fd2cf7bbbf8292e7b364a1680fd431cce5ddf8b5f300722e8a1d9234e1d0 0.600000000000 1399929 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": 941783, "vin": [ { "gen": { "height": 941773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e07fd2cf7bbbf8292e7b364a1680fd431cce5ddf8b5f300722e8a1d9234e1d0" } } ], "extra": [ 1, 232, 28, 203, 179, 141, 250, 248, 90, 253, 97, 200, 75, 166, 215, 188, 54, 5, 39, 137, 84, 226, 60, 139, 89, 12, 46, 71, 221, 82, 35, 222, 19, 2, 17, 0, 0, 0, 4, 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