Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abcef26c355ab14817b2a2c5bd839df40c512c307c8a69561e59e57f80d443fa

Tx prefix hash: 2cce92aa160395b5b61dcc125b8d63604b020ef27f083fb1909ea59cea177d32
Tx public key: 472f8e0db1442f8dcc71d39b8b1b586fc9effb34ece39a232b9abc6378d68e7d
Timestamp: 1634800407 Timestamp [UCT]: 2021-10-21 07:13:27 Age [y:d:h:m:s]: 03:067:15:03:55
Block: 357290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 826579 RingCT/type: yes/0
Extra: 01472f8e0db1442f8dcc71d39b8b1b586fc9effb34ece39a232b9abc6378d68e7d021100000004fdc024ec000000000000000000

1 output(s) for total of 40.194350902000 dcy

stealth address amount amount idx
00: 5e27a89eda67f2407ad4f861461144c95683c912fcac63b944244248a7f6d2f7 40.194350902000 728600 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": 357300, "vin": [ { "gen": { "height": 357290 } } ], "vout": [ { "amount": 40194350902, "target": { "key": "5e27a89eda67f2407ad4f861461144c95683c912fcac63b944244248a7f6d2f7" } } ], "extra": [ 1, 71, 47, 142, 13, 177, 68, 47, 141, 204, 113, 211, 155, 139, 27, 88, 111, 201, 239, 251, 52, 236, 227, 154, 35, 43, 154, 188, 99, 120, 214, 142, 125, 2, 17, 0, 0, 0, 4, 253, 192, 36, 236, 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