Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335ff2e62d92ba75edce3253bf2e7c60ad4951a26982c3bd1aa46cbad4ab78cf

Tx prefix hash: 646c3f0b9160d307f0231d49f8a4a41305d4dbef55a1b0c3d0c9bc16767a8de9
Tx public key: 1f34e059520e926178bcbdfbdf0250702458ca80df1d3df6ad9c87b5498a75b6
Timestamp: 1677462094 Timestamp [UCT]: 2023-02-27 01:41:34 Age [y:d:h:m:s]: 01:330:05:03:52
Block: 705773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496905 RingCT/type: yes/0
Extra: 011f34e059520e926178bcbdfbdf0250702458ca80df1d3df6ad9c87b5498a75b6021100000002faf35c9c000000000000000000

1 output(s) for total of 2.815016699000 dcy

stealth address amount amount idx
00: 1ea5ee5b4a4da5c7881661bac1219e26fe4b72eed15773d72af8ac47e4c5a946 2.815016699000 1149486 of 0

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": 705783, "vin": [ { "gen": { "height": 705773 } } ], "vout": [ { "amount": 2815016699, "target": { "key": "1ea5ee5b4a4da5c7881661bac1219e26fe4b72eed15773d72af8ac47e4c5a946" } } ], "extra": [ 1, 31, 52, 224, 89, 82, 14, 146, 97, 120, 188, 189, 251, 223, 2, 80, 112, 36, 88, 202, 128, 223, 29, 61, 246, 173, 156, 135, 181, 73, 138, 117, 182, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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