Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044b3adba5788e4dbb63a80a635d97a03445292408346c9f755c4c92116a5e01

Tx prefix hash: 2e7fdfcab2af24a27581aa8df2bbc5a2bc3d5cf189dcc8a23201929a95f16bdc
Tx public key: a9d55a9c870f904760388137595000456c5779dcff63acf2595acb12fdcdac5a
Timestamp: 1730799922 Timestamp [UCT]: 2024-11-05 09:45:22 Age [y:d:h:m:s]: 00:152:15:55:01
Block: 1147004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108931 RingCT/type: yes/0
Extra: 01a9d55a9c870f904760388137595000456c5779dcff63acf2595acb12fdcdac5a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6e4d044f1163ce9a8cdc908fb95068839d7d688d3d54f80383f1f821d2a1e75 0.600000000000 1631697 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": 1147014, "vin": [ { "gen": { "height": 1147004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6e4d044f1163ce9a8cdc908fb95068839d7d688d3d54f80383f1f821d2a1e75" } } ], "extra": [ 1, 169, 213, 90, 156, 135, 15, 144, 71, 96, 56, 129, 55, 89, 80, 0, 69, 108, 87, 121, 220, 255, 99, 172, 242, 89, 90, 203, 18, 253, 205, 172, 90, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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