Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0ab83aa6475ba578c0edc1fcc57309ad70ff9f2ef8d76ab628058f68e31bd13

Tx prefix hash: 3b30efc83f909b3ad06ba223d76d95a83ae22d1160f7312a44031955e57ab134
Tx public key: aa1605d3c187e5e11f190f4781b9385704c216191c42a6b03e84efc72db29d4d
Timestamp: 1748297160 Timestamp [UCT]: 2025-05-26 22:06:00 Age [y:d:h:m:s]: 00:171:10:46:26
Block: 1291610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120230 RingCT/type: yes/0
Extra: 01aa1605d3c187e5e11f190f4781b9385704c216191c42a6b03e84efc72db29d4d02110000000286ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e18db86f1a32fdaae4fc012dda9d33d668f49bc0fc3f48b2b94fd4e58d61ca1 0.600000000000 1779081 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": 1291620, "vin": [ { "gen": { "height": 1291610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e18db86f1a32fdaae4fc012dda9d33d668f49bc0fc3f48b2b94fd4e58d61ca1" } } ], "extra": [ 1, 170, 22, 5, 211, 193, 135, 229, 225, 31, 25, 15, 71, 129, 185, 56, 87, 4, 194, 22, 25, 28, 66, 166, 176, 62, 132, 239, 199, 45, 178, 157, 77, 2, 17, 0, 0, 0, 2, 134, 174, 47, 13, 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