Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da89d865d5e63195a688dae7fd42aa0c307fe077b66a31aab1e273bcf72748ef

Tx prefix hash: c996e6539c7920400ae7247907d64931d603465881f4081dfc7a81a8e3d2de62
Tx public key: 0507cf97c438197d73aa9bad4517e01754d3b8346f1303cddc4e2fe420fcb450
Timestamp: 1698890426 Timestamp [UCT]: 2023-11-02 02:00:26 Age [y:d:h:m:s]: 01:071:00:19:46
Block: 882751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311963 RingCT/type: yes/0
Extra: 010507cf97c438197d73aa9bad4517e01754d3b8346f1303cddc4e2fe420fcb450021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.729591051000 dcy

stealth address amount amount idx
00: a71e1e48bc69fbe7c7a2720b9036dad63f625d1fd2b85dc29aedf0c0f3341894 0.729591051000 1338429 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": 882761, "vin": [ { "gen": { "height": 882751 } } ], "vout": [ { "amount": 729591051, "target": { "key": "a71e1e48bc69fbe7c7a2720b9036dad63f625d1fd2b85dc29aedf0c0f3341894" } } ], "extra": [ 1, 5, 7, 207, 151, 196, 56, 25, 125, 115, 170, 155, 173, 69, 23, 224, 23, 84, 211, 184, 52, 111, 19, 3, 205, 220, 78, 47, 228, 32, 252, 180, 80, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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