Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d92e4c002aaf30894350cb49ab5e67c020a9404c1eb763403b96e32b1313805

Tx prefix hash: f668e783f94726c2f02b4c1484eb9eb52cb4149c6aefd1f3674d8a0de31da6b2
Tx public key: d16f4fb500816a2e795d8182a5f719cfd45d181a95cbe27c46cf40ea422bb378
Timestamp: 1674277816 Timestamp [UCT]: 2023-01-21 05:10:16 Age [y:d:h:m:s]: 01:299:08:34:47
Block: 679357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474921 RingCT/type: yes/0
Extra: 01d16f4fb500816a2e795d8182a5f719cfd45d181a95cbe27c46cf40ea422bb3780211000000045029cbac000000000000000000

1 output(s) for total of 3.443564231000 dcy

stealth address amount amount idx
00: 57594502c58610e63984c8a8d45a6fac142dd4898c9eb5699e6e20597364acc5 3.443564231000 1121330 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": 679367, "vin": [ { "gen": { "height": 679357 } } ], "vout": [ { "amount": 3443564231, "target": { "key": "57594502c58610e63984c8a8d45a6fac142dd4898c9eb5699e6e20597364acc5" } } ], "extra": [ 1, 209, 111, 79, 181, 0, 129, 106, 46, 121, 93, 129, 130, 165, 247, 25, 207, 212, 93, 24, 26, 149, 203, 226, 124, 70, 207, 64, 234, 66, 43, 179, 120, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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