Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1632b9ce185c065693c8eb5dabda83ba07ea4a2a8cce142ce82a17ce2bdd4bf4

Tx prefix hash: 1edcdf3e0864f08e28a8b079a8802f2094d00e271d7069d3bfd63fbbb0cd8e45
Tx public key: 970b8cdaebd77ec6ee202a229d63490405f9a524a44d1eaa51f5c8ee6edf4c57
Timestamp: 1681081434 Timestamp [UCT]: 2023-04-09 23:03:54 Age [y:d:h:m:s]: 02:070:03:04:39
Block: 735134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572216 RingCT/type: yes/0
Extra: 01970b8cdaebd77ec6ee202a229d63490405f9a524a44d1eaa51f5c8ee6edf4c57021100000003b3164c24000000000000000000

1 output(s) for total of 2.250070440000 dcy

stealth address amount amount idx
00: 6fc2275899e393169a2d7f4b0ea1df3a092bb9b2dc5152e9deb4df959b66a792 2.250070440000 1181425 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": 735144, "vin": [ { "gen": { "height": 735134 } } ], "vout": [ { "amount": 2250070440, "target": { "key": "6fc2275899e393169a2d7f4b0ea1df3a092bb9b2dc5152e9deb4df959b66a792" } } ], "extra": [ 1, 151, 11, 140, 218, 235, 215, 126, 198, 238, 32, 42, 34, 157, 99, 73, 4, 5, 249, 165, 36, 164, 77, 30, 170, 81, 245, 200, 238, 110, 223, 76, 87, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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