Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ace05709c62bd61fa92503e47ba36061fa6feaa121fb9509331d4c2d49e0b36

Tx prefix hash: c65d2faeba0071550201830b2c8ed6426c635635706018e9379f8931be1127e3
Tx public key: 84adc4281aabb2a7b608bc2740d9e0687b5f67df6c69968c9b7a897ee7a6b5e2
Timestamp: 1685628801 Timestamp [UCT]: 2023-06-01 14:13:21 Age [y:d:h:m:s]: 01:350:12:34:35
Block: 772854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511747 RingCT/type: yes/0
Extra: 0184adc4281aabb2a7b608bc2740d9e0687b5f67df6c69968c9b7a897ee7a6b5e2021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.687384443000 dcy

stealth address amount amount idx
00: 53dd2ca75b9a3854bdb6190d8ac28d707001969c96382286c2da739b8391483c 1.687384443000 1222285 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": 772864, "vin": [ { "gen": { "height": 772854 } } ], "vout": [ { "amount": 1687384443, "target": { "key": "53dd2ca75b9a3854bdb6190d8ac28d707001969c96382286c2da739b8391483c" } } ], "extra": [ 1, 132, 173, 196, 40, 26, 171, 178, 167, 182, 8, 188, 39, 64, 217, 224, 104, 123, 95, 103, 223, 108, 105, 150, 140, 155, 122, 137, 126, 231, 166, 181, 226, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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