Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed33275cfe3b611f329645e4e05f4b51e7aaef34052db7084368cab3f690745

Tx prefix hash: 59de5b32d76144665784f61814a5123e35c0d6e56731ed9bc09e729372b612c9
Tx public key: 0e939ad3086d23fe5d97fbd849b6354d4b25b38cd5004375bdc80d65886df2d8
Timestamp: 1696301183 Timestamp [UCT]: 2023-10-03 02:46:23 Age [y:d:h:m:s]: 01:178:15:19:38
Block: 861283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388722 RingCT/type: yes/0
Extra: 010e939ad3086d23fe5d97fbd849b6354d4b25b38cd5004375bdc80d65886df2d80211000000074b8f5122000000000000000000

1 output(s) for total of 0.859432802000 dcy

stealth address amount amount idx
00: 5583b7974a37ce78ca187ec93b4b674f36a41292cc9b0aded72f6ba33a34eaa5 0.859432802000 1315617 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": 861293, "vin": [ { "gen": { "height": 861283 } } ], "vout": [ { "amount": 859432802, "target": { "key": "5583b7974a37ce78ca187ec93b4b674f36a41292cc9b0aded72f6ba33a34eaa5" } } ], "extra": [ 1, 14, 147, 154, 211, 8, 109, 35, 254, 93, 151, 251, 216, 73, 182, 53, 77, 75, 37, 179, 140, 213, 0, 67, 117, 189, 200, 13, 101, 136, 109, 242, 216, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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