Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5590c1b3e6d8a27caa5c7018ad92aec13cdb7e94c6854295be5e31448fa6a7

Tx prefix hash: ee0cc3ffcf45db55677f10fab27bb5d7428939fd4a5cade8b74906eb26fc21de
Tx public key: 5549a27fe8fad855e958c0c278f298cda7dc06e86d2194c3ffad521b330211b5
Timestamp: 1673924353 Timestamp [UCT]: 2023-01-17 02:59:13 Age [y:d:h:m:s]: 02:001:10:50:29
Block: 676423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522929 RingCT/type: yes/0
Extra: 015549a27fe8fad855e958c0c278f298cda7dc06e86d2194c3ffad521b330211b50211000000015ec35160000000000000000000

1 output(s) for total of 3.521516700000 dcy

stealth address amount amount idx
00: 1bd08d18883269454e5f60bcd4e421d8e75c12c11ebcab3f2c29a82d1e8e6752 3.521516700000 1118138 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": 676433, "vin": [ { "gen": { "height": 676423 } } ], "vout": [ { "amount": 3521516700, "target": { "key": "1bd08d18883269454e5f60bcd4e421d8e75c12c11ebcab3f2c29a82d1e8e6752" } } ], "extra": [ 1, 85, 73, 162, 127, 232, 250, 216, 85, 233, 88, 192, 194, 120, 242, 152, 205, 167, 220, 6, 232, 109, 33, 148, 195, 255, 173, 82, 27, 51, 2, 17, 181, 2, 17, 0, 0, 0, 1, 94, 195, 81, 96, 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