Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65a4fc16bdc33bb609a011966282b4b4e07b259323c39bcc2e681dcfb8ab800

Tx prefix hash: ad81f7395030e9db3963f20b760f582537d4903c5b42b27002c40d4f57525c9c
Tx public key: 627779e3a5d3e6e144aec771ae9ca2142a66ea416fbfef9534051e034d7864f8
Timestamp: 1721867119 Timestamp [UCT]: 2024-07-25 00:25:19 Age [y:d:h:m:s]: 00:281:19:26:49
Block: 1073036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201339 RingCT/type: yes/0
Extra: 01627779e3a5d3e6e144aec771ae9ca2142a66ea416fbfef9534051e034d7864f802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 107f7f71619c6a163dd6a035b4d0df96bbf863d415e25b0681c864e176edca8a 0.600000000000 1545535 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": 1073046, "vin": [ { "gen": { "height": 1073036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "107f7f71619c6a163dd6a035b4d0df96bbf863d415e25b0681c864e176edca8a" } } ], "extra": [ 1, 98, 119, 121, 227, 165, 211, 230, 225, 68, 174, 199, 113, 174, 156, 162, 20, 42, 102, 234, 65, 111, 191, 239, 149, 52, 5, 30, 3, 77, 120, 100, 248, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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