Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70636c1363504daa0c46c8f77aa38d60e5b8bd8d7cd50ca7c38cd087970b7964

Tx prefix hash: 4c04253be807f927bcd751546cbbd541e05ff8f5b7d8bb3ab1a452578c6e6749
Tx public key: be056e33bcf37767ad38dddfce74c18b132c34e3d8792dbc9b61ed0469c9a017
Timestamp: 1735029606 Timestamp [UCT]: 2024-12-24 08:40:06 Age [y:d:h:m:s]: 00:083:04:13:34
Block: 1182047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59236 RingCT/type: yes/0
Extra: 01be056e33bcf37767ad38dddfce74c18b132c34e3d8792dbc9b61ed0469c9a017021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a279e6a60bfd2081b7cd8c9e6fb213d0a118824fae31871d7338c4a0ff5b44f2 0.600000000000 1668476 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": 1182057, "vin": [ { "gen": { "height": 1182047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a279e6a60bfd2081b7cd8c9e6fb213d0a118824fae31871d7338c4a0ff5b44f2" } } ], "extra": [ 1, 190, 5, 110, 51, 188, 243, 119, 103, 173, 56, 221, 223, 206, 116, 193, 139, 19, 44, 52, 227, 216, 121, 45, 188, 155, 97, 237, 4, 105, 201, 160, 23, 2, 17, 0, 0, 0, 5, 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