Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 616a0da124aa627a2a6904d775f1b28bb13ac5e14cdf8a3928c9b283fbee16da

Tx prefix hash: 3e649cdb46fd33f3f34a0ee7641f22626590729b49bfa25d14e666a21d44a998
Tx public key: 35e6b6f26bbd5b328dcaa9c2ac7674245ce5655294331c9ba85965f14859c7c7
Timestamp: 1748299605 Timestamp [UCT]: 2025-05-26 22:46:45 Age [y:d:h:m:s]: 00:228:18:06:10
Block: 1291630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161267 RingCT/type: yes/0
Extra: 0135e6b6f26bbd5b328dcaa9c2ac7674245ce5655294331c9ba85965f14859c7c702110000000486ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f689d33b7759b46cbbe331a531558a708aee671bbc5a4483f7925e0b5b6e566 0.600000000000 1779101 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": 1291640, "vin": [ { "gen": { "height": 1291630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f689d33b7759b46cbbe331a531558a708aee671bbc5a4483f7925e0b5b6e566" } } ], "extra": [ 1, 53, 230, 182, 242, 107, 189, 91, 50, 141, 202, 169, 194, 172, 118, 116, 36, 92, 229, 101, 82, 148, 51, 28, 155, 168, 89, 101, 241, 72, 89, 199, 199, 2, 17, 0, 0, 0, 4, 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