Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c05c713ce6703d1d1e783380dc95d7d4612f6af714a7c7fcb12623e5165d4a99

Tx prefix hash: aaaa049b0e8cdfbcc1f0ccb774bb2594de7263eb6720e701a8aef852f639f713
Tx public key: 7ec825f33e0cabbcc856bcf8de270976f58c3548ffdf5fa4e18bedcae6876ecc
Timestamp: 1747065536 Timestamp [UCT]: 2025-05-12 15:58:56 Age [y:d:h:m:s]: 00:191:03:53:52
Block: 1281404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134337 RingCT/type: yes/0
Extra: 017ec825f33e0cabbcc856bcf8de270976f58c3548ffdf5fa4e18bedcae6876ecc0211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 499409addf0a7d93d6bbf996c0ac66da5b4a2ae4c248c0058bdbfbd2c0eeeea9 0.600000000000 1768803 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": 1281414, "vin": [ { "gen": { "height": 1281404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499409addf0a7d93d6bbf996c0ac66da5b4a2ae4c248c0058bdbfbd2c0eeeea9" } } ], "extra": [ 1, 126, 200, 37, 243, 62, 12, 171, 188, 200, 86, 188, 248, 222, 39, 9, 118, 245, 140, 53, 72, 255, 223, 95, 164, 225, 139, 237, 202, 230, 135, 110, 204, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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