Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad12db628622a2d9758e964d9a83fbd1e07ecc526020b4c74b7b77f898a9ffc5

Tx prefix hash: 907e1bc13796cbae31b5bb0cf6532de757625d8544e27be982b020163f10ae0b
Tx public key: 879a9c4db04956d6ff659daeb930f5bdba80c37f65f279224ebde4669d282661
Timestamp: 1710353295 Timestamp [UCT]: 2024-03-13 18:08:15 Age [y:d:h:m:s]: 01:022:01:20:00
Block: 977596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276733 RingCT/type: yes/0
Extra: 01879a9c4db04956d6ff659daeb930f5bdba80c37f65f279224ebde4669d28266102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa5b2ea79cfbbdf05fcf4f7e5856f5b1c63928b7ef1e46dda156932b452ab89f 0.600000000000 1437599 of 15

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": 977606, "vin": [ { "gen": { "height": 977596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa5b2ea79cfbbdf05fcf4f7e5856f5b1c63928b7ef1e46dda156932b452ab89f" } } ], "extra": [ 1, 135, 154, 156, 77, 176, 73, 86, 214, 255, 101, 157, 174, 185, 48, 245, 189, 186, 128, 195, 127, 101, 242, 121, 34, 78, 189, 228, 102, 157, 40, 38, 97, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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