Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7271a4ff66875e38f4eeea921dab55c2ce6d1e78f7214bf75c247e362f0631c4

Tx prefix hash: b55aeff16e148d77fe79133e4b96bfa25a3436e50bb80a66e3d6bf0887c8f925
Tx public key: cd0ea8a9530f57bff67a3ab8e573db501fbdd0b01e3ded89dfd44c747e7b8f61
Timestamp: 1708256590 Timestamp [UCT]: 2024-02-18 11:43:10 Age [y:d:h:m:s]: 01:036:03:20:01
Block: 960197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286844 RingCT/type: yes/0
Extra: 01cd0ea8a9530f57bff67a3ab8e573db501fbdd0b01e3ded89dfd44c747e7b8f610211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 050ca605daee88cf6704502cae3662d81bbe3ffe138d48ae810d318448d21fc9 0.600000000000 1419758 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": 960207, "vin": [ { "gen": { "height": 960197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "050ca605daee88cf6704502cae3662d81bbe3ffe138d48ae810d318448d21fc9" } } ], "extra": [ 1, 205, 14, 168, 169, 83, 15, 87, 191, 246, 122, 58, 184, 229, 115, 219, 80, 31, 189, 208, 176, 30, 61, 237, 137, 223, 212, 76, 116, 126, 123, 143, 97, 2, 17, 0, 0, 0, 2, 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