Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d2594c55e90316f10658cd147b7a77402afd7c0516f4bc977e2ef570d0ddd2a

Tx prefix hash: 2fb57688b96819db4d769c9e6def51e5b60e65de186876fb39ab88b28f130a6e
Tx public key: 886c1b2564419e45b09bb2b4a419b8fbce7ca8d45cba9a726f8f0ecf19d9446c
Timestamp: 1682575343 Timestamp [UCT]: 2023-04-27 06:02:23 Age [y:d:h:m:s]: 01:345:09:35:37
Block: 747537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508102 RingCT/type: yes/0
Extra: 01886c1b2564419e45b09bb2b4a419b8fbce7ca8d45cba9a726f8f0ecf19d9446c021100000002b3164c24000000000000000000

1 output(s) for total of 2.046914999000 dcy

stealth address amount amount idx
00: 68bbaae350f263c94e9bd7af10316e0893c58344e7390fb3d70886ed97b1268b 2.046914999000 1195220 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": 747547, "vin": [ { "gen": { "height": 747537 } } ], "vout": [ { "amount": 2046914999, "target": { "key": "68bbaae350f263c94e9bd7af10316e0893c58344e7390fb3d70886ed97b1268b" } } ], "extra": [ 1, 136, 108, 27, 37, 100, 65, 158, 69, 176, 155, 178, 180, 164, 25, 184, 251, 206, 124, 168, 212, 92, 186, 154, 114, 111, 143, 14, 207, 25, 217, 68, 108, 2, 17, 0, 0, 0, 2, 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