Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba6bcaec3739b73d30d584cec262e222d1f74de077a4dc8475dfae06077bed1

Tx prefix hash: b2f27efe5f251ed7b446444418f3f80beeaca39c658f9d5a9c347b18ba1a4ede
Tx public key: 2530f7ea08a6c454856f51c74f9a7c8e9c782799979474101440b093d73b016e
Timestamp: 1675531278 Timestamp [UCT]: 2023-02-04 17:21:18 Age [y:d:h:m:s]: 02:072:02:59:02
Block: 689779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573160 RingCT/type: yes/0
Extra: 012530f7ea08a6c454856f51c74f9a7c8e9c782799979474101440b093d73b016e0211000000075029cbac000000000000000000

1 output(s) for total of 3.180356176000 dcy

stealth address amount amount idx
00: 5b00cc813cd38db04fba69e335e035c037aabcbdb883e2523403470a966ae25d 3.180356176000 1132481 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": 689789, "vin": [ { "gen": { "height": 689779 } } ], "vout": [ { "amount": 3180356176, "target": { "key": "5b00cc813cd38db04fba69e335e035c037aabcbdb883e2523403470a966ae25d" } } ], "extra": [ 1, 37, 48, 247, 234, 8, 166, 196, 84, 133, 111, 81, 199, 79, 154, 124, 142, 156, 120, 39, 153, 151, 148, 116, 16, 20, 64, 176, 147, 215, 59, 1, 110, 2, 17, 0, 0, 0, 7, 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