Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5c55a39b8965ae14d8019b722f6679b198da6ef1f3f243697edbcf00c3d08b

Tx prefix hash: 7bed65e0c1032c15f325bef23e81661fcd1faa37118ab868eceb3edccbb522d5
Tx public key: ddfc2227c229281a3c5d1ad71e9aeb74ca77a6935a8cec38623b43fdc1671c18
Timestamp: 1733222534 Timestamp [UCT]: 2024-12-03 10:42:14 Age [y:d:h:m:s]: 00:118:04:01:47
Block: 1167076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84249 RingCT/type: yes/0
Extra: 01ddfc2227c229281a3c5d1ad71e9aeb74ca77a6935a8cec38623b43fdc1671c180211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f5520f98176d3a185a322b8d3ddbba26e6c93ee2abe027024e6ae86e950adc7 0.600000000000 1652769 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": 1167086, "vin": [ { "gen": { "height": 1167076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f5520f98176d3a185a322b8d3ddbba26e6c93ee2abe027024e6ae86e950adc7" } } ], "extra": [ 1, 221, 252, 34, 39, 194, 41, 40, 26, 60, 93, 26, 215, 30, 154, 235, 116, 202, 119, 166, 147, 90, 140, 236, 56, 98, 59, 67, 253, 193, 103, 28, 24, 2, 17, 0, 0, 0, 4, 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