Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53df4c4b85553e8f0cc9e03c51c099a3bae51cca5c29c8802adf394b72895458

Tx prefix hash: 01e3d0722954d8db9f09a36275878574e7cc7844736478d34c70e0090645144c
Tx public key: 3ca1638ec95ec1e3a4ef11726d12a8010a9fcd8a6069dcf42b0fe59bee0c6e7f
Timestamp: 1706248484 Timestamp [UCT]: 2024-01-26 05:54:44 Age [y:d:h:m:s]: 01:030:15:16:18
Block: 943519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282955 RingCT/type: yes/0
Extra: 013ca1638ec95ec1e3a4ef11726d12a8010a9fcd8a6069dcf42b0fe59bee0c6e7f02110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e7909ce83b98868a970f68abeab7f23b74000e40f362eb69a1ef0ae2118d8b9 0.600000000000 1401727 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": 943529, "vin": [ { "gen": { "height": 943519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e7909ce83b98868a970f68abeab7f23b74000e40f362eb69a1ef0ae2118d8b9" } } ], "extra": [ 1, 60, 161, 99, 142, 201, 94, 193, 227, 164, 239, 17, 114, 109, 18, 168, 1, 10, 159, 205, 138, 96, 105, 220, 244, 43, 15, 229, 155, 238, 12, 110, 127, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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