Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 100cc9d0a466a00a22a0bfa96c2ea5052a2e551150d430b135cc5f06feaa6fee

Tx prefix hash: f94e1f3ffaeea5f06acb2ffce74b5ebc6762c292e793d8cc233d70ab020ccb94
Tx public key: febbf2934f2795822b7f140767d5a2956aa87dea3b703e6a43cb14622c40ac2e
Timestamp: 1726840344 Timestamp [UCT]: 2024-09-20 13:52:24 Age [y:d:h:m:s]: 00:238:17:54:54
Block: 1114264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170482 RingCT/type: yes/0
Extra: 01febbf2934f2795822b7f140767d5a2956aa87dea3b703e6a43cb14622c40ac2e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c33bc175d4f01bb0373707d55db8f31c912fe6b9a4de11068b55d47534302e3 0.600000000000 1594063 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": 1114274, "vin": [ { "gen": { "height": 1114264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c33bc175d4f01bb0373707d55db8f31c912fe6b9a4de11068b55d47534302e3" } } ], "extra": [ 1, 254, 187, 242, 147, 79, 39, 149, 130, 43, 127, 20, 7, 103, 213, 162, 149, 106, 168, 125, 234, 59, 112, 62, 106, 67, 203, 20, 98, 44, 64, 172, 46, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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