Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3276e1460540ca436cfe82f861d75c840e435cc594009e1b116496aecc059f6

Tx prefix hash: 3b28497d5bd9744e91bfd2d1e5045dbb5c1464ba29d1944fb33fb96bd91e074c
Tx public key: fbc83c4b3c4c658d796f295aa8555f192274e364d14e97f3f4f2ffd69ade8eaa
Timestamp: 1699370666 Timestamp [UCT]: 2023-11-07 15:24:26 Age [y:d:h:m:s]: 01:162:23:18:12
Block: 886532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377677 RingCT/type: yes/0
Extra: 01fbc83c4b3c4c658d796f295aa8555f192274e364d14e97f3f4f2ffd69ade8eaa02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.708845310000 dcy

stealth address amount amount idx
00: 2ec6293730c940f0ccc42f079d23fdee1cbc3c03d2e85a0710c4584936f41ad0 0.708845310000 1342359 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": 886542, "vin": [ { "gen": { "height": 886532 } } ], "vout": [ { "amount": 708845310, "target": { "key": "2ec6293730c940f0ccc42f079d23fdee1cbc3c03d2e85a0710c4584936f41ad0" } } ], "extra": [ 1, 251, 200, 60, 75, 60, 76, 101, 141, 121, 111, 41, 90, 168, 85, 95, 25, 34, 116, 227, 100, 209, 78, 151, 243, 244, 242, 255, 214, 154, 222, 142, 170, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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