Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef95c43bbff6cee184d28a56fd9c37ef9f142b6930f29bfc1b0eee9bce2c6608

Tx prefix hash: 3edb81c3e5ebfa9287ba122d590070a9710423b0ed33dcfd0cf4a6a2fa448f8b
Tx public key: c33d2de6d9b2cb312f4682e73732dd29d6d9d2201903e041e4a7c6ab1b8c13f7
Timestamp: 1681350049 Timestamp [UCT]: 2023-04-13 01:40:49 Age [y:d:h:m:s]: 02:209:12:09:43
Block: 737360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669609 RingCT/type: yes/0
Extra: 01c33d2de6d9b2cb312f4682e73732dd29d6d9d2201903e041e4a7c6ab1b8c13f70211000000015029cbac000000000000000000

1 output(s) for total of 2.212179936000 dcy

stealth address amount amount idx
00: d7882abcc93eb715b49a6629cb91ee35f0bb15d3c366e38ac57cf1f23d0ee714 2.212179936000 1183907 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": 737370, "vin": [ { "gen": { "height": 737360 } } ], "vout": [ { "amount": 2212179936, "target": { "key": "d7882abcc93eb715b49a6629cb91ee35f0bb15d3c366e38ac57cf1f23d0ee714" } } ], "extra": [ 1, 195, 61, 45, 230, 217, 178, 203, 49, 47, 70, 130, 231, 55, 50, 221, 41, 214, 217, 210, 32, 25, 3, 224, 65, 228, 167, 198, 171, 27, 140, 19, 247, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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