Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5906894f46b04cdf0d6668b7959925e6a4dd631e34e205f4b595f9358ed7c17d

Tx prefix hash: 8d50bdb7f8dcd3cb360ba928cbb57e27ff93e0924fb6aca08f7d46ad5810c35e
Tx public key: 9f5b21b22e5fd8ac441eb73fafc55ea9d90f1c08e64fb215ca0f6783fae7d624
Timestamp: 1712139101 Timestamp [UCT]: 2024-04-03 10:11:41 Age [y:d:h:m:s]: 01:245:03:22:58
Block: 992354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433961 RingCT/type: yes/0
Extra: 019f5b21b22e5fd8ac441eb73fafc55ea9d90f1c08e64fb215ca0f6783fae7d6240211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2b9a56c87e2c1aa4417da81a828096056aed7e3270e61223be76ab564c198bc 0.600000000000 1452694 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": 992364, "vin": [ { "gen": { "height": 992354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2b9a56c87e2c1aa4417da81a828096056aed7e3270e61223be76ab564c198bc" } } ], "extra": [ 1, 159, 91, 33, 178, 46, 95, 216, 172, 68, 30, 183, 63, 175, 197, 94, 169, 217, 15, 28, 8, 230, 79, 178, 21, 202, 15, 103, 131, 250, 231, 214, 36, 2, 17, 0, 0, 0, 2, 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