Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367d28073ebabfaa99d1265fe89e1e40f7ccf7a9bc9dd18ceb1faeabdc1c1eca

Tx prefix hash: 95f19b53453f1e29f2e3071c10d59e2269013560156092d9e909ba36df8ce51b
Tx public key: 887807b07b2a83df8c04a09dabe6e94fb75b5f2697ce6d8500e3e26c0c72ae22
Timestamp: 1724739284 Timestamp [UCT]: 2024-08-27 06:14:44 Age [y:d:h:m:s]: 00:220:13:20:52
Block: 1096837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157494 RingCT/type: yes/0
Extra: 01887807b07b2a83df8c04a09dabe6e94fb75b5f2697ce6d8500e3e26c0c72ae22021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9939da75f74edac9454d629b31bade37f79ff21aaaad931778061cb757c09ab 0.600000000000 1572032 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": 1096847, "vin": [ { "gen": { "height": 1096837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9939da75f74edac9454d629b31bade37f79ff21aaaad931778061cb757c09ab" } } ], "extra": [ 1, 136, 120, 7, 176, 123, 42, 131, 223, 140, 4, 160, 157, 171, 230, 233, 79, 183, 91, 95, 38, 151, 206, 109, 133, 0, 227, 226, 108, 12, 114, 174, 34, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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