Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b6bd6f6855ba7565d70bda1886f7579e034a95184814426c76f3e3178b287f5

Tx prefix hash: 9ae74b8b9604bdfea5182c9145506ae4e5a32527ede6667b176f43422838a5e1
Tx public key: 06fc7f066325709eb0a51ba26730ff4b52b73acd50cec3ec8475d2314dd080b4
Timestamp: 1713183106 Timestamp [UCT]: 2024-04-15 12:11:46 Age [y:d:h:m:s]: 00:353:18:28:07
Block: 1001035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252916 RingCT/type: yes/0
Extra: 0106fc7f066325709eb0a51ba26730ff4b52b73acd50cec3ec8475d2314dd080b40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e1141ef0b3ebd1305b338a56668e865fb261ba1d54a4e693e7ae629eeb545ba 0.600000000000 1461537 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": 1001045, "vin": [ { "gen": { "height": 1001035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e1141ef0b3ebd1305b338a56668e865fb261ba1d54a4e693e7ae629eeb545ba" } } ], "extra": [ 1, 6, 252, 127, 6, 99, 37, 112, 158, 176, 165, 27, 162, 103, 48, 255, 75, 82, 183, 58, 205, 80, 206, 195, 236, 132, 117, 210, 49, 77, 208, 128, 180, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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