Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c1b524e5a2987380c3b671dbec75877b7671109dca954b505c85e316ef2538f

Tx prefix hash: 4e03fa5bb808d2476e001a69715d009a4436b04f70d3ce145ebf47ddd0a1a3a4
Tx public key: 7eb76b95b88e9d54ee51be43f86b84cb9f37f1e3ac85abac9293e593644b8535
Timestamp: 1670310810 Timestamp [UCT]: 2022-12-06 07:13:30 Age [y:d:h:m:s]: 01:337:11:27:28
Block: 646500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502211 RingCT/type: yes/0
Extra: 017eb76b95b88e9d54ee51be43f86b84cb9f37f1e3ac85abac9293e593644b853502110000000375e3f0e9000000000000000000

1 output(s) for total of 4.424631601000 dcy

stealth address amount amount idx
00: 9dfec83a93c1814e68843d45c376dfe58cc6597e55d5434fe7139d24a85933c2 4.424631601000 1086721 of 0

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": 646510, "vin": [ { "gen": { "height": 646500 } } ], "vout": [ { "amount": 4424631601, "target": { "key": "9dfec83a93c1814e68843d45c376dfe58cc6597e55d5434fe7139d24a85933c2" } } ], "extra": [ 1, 126, 183, 107, 149, 184, 142, 157, 84, 238, 81, 190, 67, 248, 107, 132, 203, 159, 55, 241, 227, 172, 133, 171, 172, 146, 147, 229, 147, 100, 75, 133, 53, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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