Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7aefb3ceead42bdbb026c0168a512106d4b94d976ab92f624fc4b2a78f713e3

Tx prefix hash: faa5a4a177ebe7f1389dad48589b213ce0d4cd232a1148c4c5e4ddb32e11bbca
Tx public key: 2771e3b1bae5e1cc2c7a2f3952e20897d09efbe35ef9f5493c63d07bd005f8ae
Timestamp: 1764383080 Timestamp [UCT]: 2025-11-29 02:24:40 Age [y:d:h:m:s]: 00:037:20:29:25
Block: 1422389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27122 RingCT/type: yes/0
Extra: 012771e3b1bae5e1cc2c7a2f3952e20897d09efbe35ef9f5493c63d07bd005f8ae02110000000534af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0877fb8641766ed83099bf7b2f52e46824d181409f2328bb941152dc4886f067 0.600000000000 1910954 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": 1422399, "vin": [ { "gen": { "height": 1422389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0877fb8641766ed83099bf7b2f52e46824d181409f2328bb941152dc4886f067" } } ], "extra": [ 1, 39, 113, 227, 177, 186, 229, 225, 204, 44, 122, 47, 57, 82, 226, 8, 151, 208, 158, 251, 227, 94, 249, 245, 73, 60, 99, 208, 123, 208, 5, 248, 174, 2, 17, 0, 0, 0, 5, 52, 175, 49, 204, 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