Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1454a5d664c27e7efd3ac12e52b45346fd22b367ce489cc2a6128cb1264d2e9

Tx prefix hash: f97b9811daba171475382d2327f00341620b806ad1188a038847007698bc44b6
Tx public key: 6e30080654b5e76e76fd9d9734a6654a35e4eeb525615f7b28339e42bc4816aa
Timestamp: 1676386377 Timestamp [UCT]: 2023-02-14 14:52:57 Age [y:d:h:m:s]: 02:058:04:43:52
Block: 696869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 563188 RingCT/type: yes/0
Extra: 016e30080654b5e76e76fd9d9734a6654a35e4eeb525615f7b28339e42bc4816aa0211000000015029cbac000000000000000000

1 output(s) for total of 3.012892503000 dcy

stealth address amount amount idx
00: 2f80f889633e6778c6c8a5636a9c477c5d2a9fb9325b0236a7e61a849ba00fd2 3.012892503000 1139926 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": 696879, "vin": [ { "gen": { "height": 696869 } } ], "vout": [ { "amount": 3012892503, "target": { "key": "2f80f889633e6778c6c8a5636a9c477c5d2a9fb9325b0236a7e61a849ba00fd2" } } ], "extra": [ 1, 110, 48, 8, 6, 84, 181, 231, 110, 118, 253, 157, 151, 52, 166, 101, 74, 53, 228, 238, 181, 37, 97, 95, 123, 40, 51, 158, 66, 188, 72, 22, 170, 2, 17, 0, 0, 0, 1, 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