Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a34c09a8fd7afaab84746240d9f335309ba06d8b643b2416fb4ab45d4825319a

Tx prefix hash: 88508b534eda79f8ecbb9b34ddc69efc660ab8e60328d2e757d984e316f404ee
Tx public key: 4420fc2833ac655b4f3d1900b4685bd5dc3b762856e9807e96cb94832846a633
Timestamp: 1676382695 Timestamp [UCT]: 2023-02-14 13:51:35 Age [y:d:h:m:s]: 02:055:14:30:04
Block: 696839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561337 RingCT/type: yes/0
Extra: 014420fc2833ac655b4f3d1900b4685bd5dc3b762856e9807e96cb94832846a63302110000000883600029000000000000000000

1 output(s) for total of 3.013582181000 dcy

stealth address amount amount idx
00: e84953c7cb113d2538d47a62bf4e7ae4bf8006697f44f17b3d23d9d718c5665a 3.013582181000 1139896 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": 696849, "vin": [ { "gen": { "height": 696839 } } ], "vout": [ { "amount": 3013582181, "target": { "key": "e84953c7cb113d2538d47a62bf4e7ae4bf8006697f44f17b3d23d9d718c5665a" } } ], "extra": [ 1, 68, 32, 252, 40, 51, 172, 101, 91, 79, 61, 25, 0, 180, 104, 91, 213, 220, 59, 118, 40, 86, 233, 128, 126, 150, 203, 148, 131, 40, 70, 166, 51, 2, 17, 0, 0, 0, 8, 131, 96, 0, 41, 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