Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2921eec5e1f0bc2e80fb751f4fad81af1fe692b04bdfa5db95565870af3a684a

Tx prefix hash: 9289ba704175aa6fb9127f50369bb3d1d581fedb644963f7c6df2faefbfa58ae
Tx public key: 7d76e00eab2f799e3190b356882d781980f5e21cb95e6b77c5786c4e210a706c
Timestamp: 1723903128 Timestamp [UCT]: 2024-08-17 13:58:48 Age [y:d:h:m:s]: 00:294:14:31:26
Block: 1089919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210468 RingCT/type: yes/0
Extra: 017d76e00eab2f799e3190b356882d781980f5e21cb95e6b77c5786c4e210a706c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd4729726fdd1602be099ae10c5342e71561fc19c9c89555ed525f7fc2234a2b 0.600000000000 1564542 of 15

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": 1089929, "vin": [ { "gen": { "height": 1089919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4729726fdd1602be099ae10c5342e71561fc19c9c89555ed525f7fc2234a2b" } } ], "extra": [ 1, 125, 118, 224, 14, 171, 47, 121, 158, 49, 144, 179, 86, 136, 45, 120, 25, 128, 245, 226, 28, 185, 94, 107, 119, 197, 120, 108, 78, 33, 10, 112, 108, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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