Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb10e7d8a5c34c048e572e934182f8ce3e636f133cdc6cf0e61b8345d860172

Tx prefix hash: 6536ca8ecb1049c696744087a5f783cb9ba536183a0e27faf9ede6f836acb37f
Tx public key: 01e051d838195c1f3b7e89245b6022f3441078fce4db727f5170ac9bbaf4b9f1
Timestamp: 1706806557 Timestamp [UCT]: 2024-02-01 16:55:57 Age [y:d:h:m:s]: 00:273:02:21:06
Block: 948159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195554 RingCT/type: yes/0
Extra: 0101e051d838195c1f3b7e89245b6022f3441078fce4db727f5170ac9bbaf4b9f102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a16d1ee8195abe7cfe6438e12d3a9a78fdc9c762d793628d1ec8703052b948e1 0.600000000000 1406531 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": 948169, "vin": [ { "gen": { "height": 948159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a16d1ee8195abe7cfe6438e12d3a9a78fdc9c762d793628d1ec8703052b948e1" } } ], "extra": [ 1, 1, 224, 81, 216, 56, 25, 92, 31, 59, 126, 137, 36, 91, 96, 34, 243, 68, 16, 120, 252, 228, 219, 114, 127, 81, 112, 172, 155, 186, 244, 185, 241, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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