Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ae2aac24080019a82f9d9c7b5027b041aa6f662c159e0cd4f3681e717cdd5b6

Tx prefix hash: 776bde5f656802bf9ac2df79b03102cc3744175517fc59ad5dc2a6ee9270129c
Tx public key: 4b2fde1a80e9a6568e5ec882636befd34131cefa5ff6062c6581508da3f7637e
Timestamp: 1729671623 Timestamp [UCT]: 2024-10-23 08:20:23 Age [y:d:h:m:s]: 00:141:22:24:51
Block: 1137707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101242 RingCT/type: yes/0
Extra: 014b2fde1a80e9a6568e5ec882636befd34131cefa5ff6062c6581508da3f7637e021100000001dcb45f33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aef98e63767541652ae91e0cc7f9748aa67cfb6ceff9accc34d580007ff2568b 0.600000000000 1621248 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": 1137717, "vin": [ { "gen": { "height": 1137707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef98e63767541652ae91e0cc7f9748aa67cfb6ceff9accc34d580007ff2568b" } } ], "extra": [ 1, 75, 47, 222, 26, 128, 233, 166, 86, 142, 94, 200, 130, 99, 107, 239, 211, 65, 49, 206, 250, 95, 246, 6, 44, 101, 129, 80, 141, 163, 247, 99, 126, 2, 17, 0, 0, 0, 1, 220, 180, 95, 51, 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