Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e8f4a3b19ee1aa8187960cd5c1133e66be175f9866b180681b811cae2783823

Tx prefix hash: 8ffc87e4bf494e9f85915d220e1398d0bf2402fdcd029a7ff1443373b0d1ada5
Tx public key: 3b6338a2ed2ab5635c24bdd7be5c4a7cc88ed8aef251ff3e12e40d57f8840deb
Timestamp: 1707088833 Timestamp [UCT]: 2024-02-04 23:20:33 Age [y:d:h:m:s]: 01:062:09:02:17
Block: 950501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305639 RingCT/type: yes/0
Extra: 013b6338a2ed2ab5635c24bdd7be5c4a7cc88ed8aef251ff3e12e40d57f8840deb0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a35450d5a88e23f33ee2c24bbdf64b7e048e28cb140c67c7f8b433f983f546 0.600000000000 1409133 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": 950511, "vin": [ { "gen": { "height": 950501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a35450d5a88e23f33ee2c24bbdf64b7e048e28cb140c67c7f8b433f983f546" } } ], "extra": [ 1, 59, 99, 56, 162, 237, 42, 181, 99, 92, 36, 189, 215, 190, 92, 74, 124, 200, 142, 216, 174, 242, 81, 255, 62, 18, 228, 13, 87, 248, 132, 13, 235, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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