Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3612d40badecc5c76323c0d2a6e7c14aaa08f830e4f679e9e23f60bdf54dceb

Tx prefix hash: b0574d18f0e6d9e5d8a901b92894cfba210f8c1e5a5df52d449d69f0f9d2a7f4
Tx public key: 7485bbb2281bd783684d6b75a90182740b74e9beebbbcd29e2cf649de0cfde80
Timestamp: 1707938091 Timestamp [UCT]: 2024-02-14 19:14:51 Age [y:d:h:m:s]: 01:010:14:35:16
Block: 957548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268591 RingCT/type: yes/0
Extra: 017485bbb2281bd783684d6b75a90182740b74e9beebbbcd29e2cf649de0cfde800211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c41e24c28b8f9e4fa9db683b71dc0631f1e5a9494b597d0a8955fc16b0496591 0.600000000000 1416866 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": 957558, "vin": [ { "gen": { "height": 957548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c41e24c28b8f9e4fa9db683b71dc0631f1e5a9494b597d0a8955fc16b0496591" } } ], "extra": [ 1, 116, 133, 187, 178, 40, 27, 215, 131, 104, 77, 107, 117, 169, 1, 130, 116, 11, 116, 233, 190, 235, 187, 205, 41, 226, 207, 100, 157, 224, 207, 222, 128, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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