Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fd3a0edc23e962bb7d6956cb53783f40d515101fd68a2b841456dd2fb6a8086

Tx prefix hash: c5ecbdfbc7d30d7b59cbfdb518854f1195dccc98f66458434a111c108e992ef9
Tx public key: 9b9e147b87e28354bb34637f6fd5f45dd195a6bf766172affe8710b9aa587ba6
Timestamp: 1735201870 Timestamp [UCT]: 2024-12-26 08:31:10 Age [y:d:h:m:s]: 00:083:13:34:41
Block: 1183467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59528 RingCT/type: yes/0
Extra: 019b9e147b87e28354bb34637f6fd5f45dd195a6bf766172affe8710b9aa587ba6021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b796f2e201d8043482a2cafa1e9ea309ba891fc798a2e3fe2edb1a4b7f720737 0.600000000000 1669912 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": 1183477, "vin": [ { "gen": { "height": 1183467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b796f2e201d8043482a2cafa1e9ea309ba891fc798a2e3fe2edb1a4b7f720737" } } ], "extra": [ 1, 155, 158, 20, 123, 135, 226, 131, 84, 187, 52, 99, 127, 111, 213, 244, 93, 209, 149, 166, 191, 118, 97, 114, 175, 254, 135, 16, 185, 170, 88, 123, 166, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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