Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44cc18cead76e077012b966f31f083f687add214a311e64ea39871d63553ac5b

Tx prefix hash: 248abf8d444307d3eba40103d7745930a57ec4cb4adc0803396a12e4d200ffc1
Tx public key: 011dca7ecfb81959c7a9e06d7a969a9a08215d2c5f0854adbc04d94a4e80ff63
Timestamp: 1734482980 Timestamp [UCT]: 2024-12-18 00:49:40 Age [y:d:h:m:s]: 00:114:02:51:15
Block: 1177544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81328 RingCT/type: yes/0
Extra: 01011dca7ecfb81959c7a9e06d7a969a9a08215d2c5f0854adbc04d94a4e80ff63021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3d70c4888090ccd5308faa50938dbee5a43a2ef28dedbb2cd4484a279bb2205 0.600000000000 1663915 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": 1177554, "vin": [ { "gen": { "height": 1177544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3d70c4888090ccd5308faa50938dbee5a43a2ef28dedbb2cd4484a279bb2205" } } ], "extra": [ 1, 1, 29, 202, 126, 207, 184, 25, 89, 199, 169, 224, 109, 122, 150, 154, 154, 8, 33, 93, 44, 95, 8, 84, 173, 188, 4, 217, 74, 78, 128, 255, 99, 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