Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58b2e0fe4319a2bc66fb43e7060e67a33073e3aed634a147623cff3e56dc2fd

Tx prefix hash: 17aca1948cf5bc4c1c9e554b1e1a7981b62416e5e84d48139f4902e7eea9441b
Tx public key: ecaecdb86e46764dc09dcc16ca2f18364991f78ea892477f96d109bcd6d55e94
Timestamp: 1736386256 Timestamp [UCT]: 2025-01-09 01:30:56 Age [y:d:h:m:s]: 00:076:13:49:09
Block: 1193273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54479 RingCT/type: yes/0
Extra: 01ecaecdb86e46764dc09dcc16ca2f18364991f78ea892477f96d109bcd6d55e94021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81dfcc419cab6c5ee580b0a6049fe42daa8b5558e2c64dceff4eeb6c0909caa0 0.600000000000 1679832 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": 1193283, "vin": [ { "gen": { "height": 1193273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81dfcc419cab6c5ee580b0a6049fe42daa8b5558e2c64dceff4eeb6c0909caa0" } } ], "extra": [ 1, 236, 174, 205, 184, 110, 70, 118, 77, 192, 157, 204, 22, 202, 47, 24, 54, 73, 145, 247, 142, 168, 146, 71, 127, 150, 209, 9, 188, 214, 213, 94, 148, 2, 17, 0, 0, 0, 4, 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