Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 989e2f02e277bd8a063c5a72fe9885161de24fbf95c4d11f833f01612f5323c7

Tx prefix hash: eec0caa4c12813d96c716044485dc483c70eb1a102293771a0d06eed1999f1b1
Tx public key: b0247093bf0d25e8cbb72b63b43ff5410f56c99ff27e707f2cadc68d9268f1d7
Timestamp: 1733407298 Timestamp [UCT]: 2024-12-05 14:01:38 Age [y:d:h:m:s]: 00:192:19:41:32
Block: 1168607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137548 RingCT/type: yes/0
Extra: 01b0247093bf0d25e8cbb72b63b43ff5410f56c99ff27e707f2cadc68d9268f1d7021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c83e9d93dc9642aeec5f6d4fdbe8f1f02e71199467e7964ee3b74fa60c08ad36 0.600000000000 1654318 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": 1168617, "vin": [ { "gen": { "height": 1168607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c83e9d93dc9642aeec5f6d4fdbe8f1f02e71199467e7964ee3b74fa60c08ad36" } } ], "extra": [ 1, 176, 36, 112, 147, 191, 13, 37, 232, 203, 183, 43, 99, 180, 63, 245, 65, 15, 86, 201, 159, 242, 126, 112, 127, 44, 173, 198, 141, 146, 104, 241, 215, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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