Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36253f339471a994f1669633ff071eb2976d34203829273fc92d70ee9666bde4

Tx prefix hash: 1650ca9a1143c9a3e039f5502413a3c8cc5d1886dc2002b32707e750ce11e08f
Tx public key: ae0b8556d0b041047fa7c49b224cb047b43280a182119f795d97e94dc121049b
Timestamp: 1721450585 Timestamp [UCT]: 2024-07-20 04:43:05 Age [y:d:h:m:s]: 00:096:07:28:58
Block: 1069618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68916 RingCT/type: yes/0
Extra: 01ae0b8556d0b041047fa7c49b224cb047b43280a182119f795d97e94dc121049b021100000002162613aa000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: e22cc1536aff3d41ab77d27b7f6889db316d89f2867423f1d1b8bb3aa1af1175 0.615610000000 1541103 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": 1069628, "vin": [ { "gen": { "height": 1069618 } } ], "vout": [ { "amount": 615610000, "target": { "key": "e22cc1536aff3d41ab77d27b7f6889db316d89f2867423f1d1b8bb3aa1af1175" } } ], "extra": [ 1, 174, 11, 133, 86, 208, 176, 65, 4, 127, 167, 196, 155, 34, 76, 176, 71, 180, 50, 128, 161, 130, 17, 159, 121, 93, 151, 233, 77, 193, 33, 4, 155, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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