Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 593d0f44add1e8f32b0d417c741807a1a82ed7fdde3d78157f9bbaf90f007abd

Tx prefix hash: e46aff5eb0eefac68c05594f1cb4a5892d7fca14fa8f31bba797b98e1f507579
Tx public key: 99121d1be8175cfe5b5dcb98d4902102de5b15fa5c2a80b6715e26ae969703a9
Timestamp: 1681143948 Timestamp [UCT]: 2023-04-10 16:25:48 Age [y:d:h:m:s]: 01:321:13:52:18
Block: 735662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491079 RingCT/type: yes/0
Extra: 0199121d1be8175cfe5b5dcb98d4902102de5b15fa5c2a80b6715e26ae969703a9021100000001b3164c24000000000000000000

1 output(s) for total of 2.241064633000 dcy

stealth address amount amount idx
00: 47106f90abab96d0bdee654c6ad9ff5d8adbbbf0922929f57c38f745f634a53c 2.241064633000 1182009 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": 735672, "vin": [ { "gen": { "height": 735662 } } ], "vout": [ { "amount": 2241064633, "target": { "key": "47106f90abab96d0bdee654c6ad9ff5d8adbbbf0922929f57c38f745f634a53c" } } ], "extra": [ 1, 153, 18, 29, 27, 232, 23, 92, 254, 91, 93, 203, 152, 212, 144, 33, 2, 222, 91, 21, 250, 92, 42, 128, 182, 113, 94, 38, 174, 150, 151, 3, 169, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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