Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b926649b648704b23b5308d206c1e92506f97898104c1879dc9fa55753e4b705

Tx prefix hash: 8d67ccf6382691a557d3d184080d90e699a0c37b2c426fd0fa5ec6e8144c58b5
Tx public key: cf9936ae152679e8b6c22bae832e4b9e79418b49c3793d10b23da4af0839dd88
Timestamp: 1731146506 Timestamp [UCT]: 2024-11-09 10:01:46 Age [y:d:h:m:s]: 00:159:03:00:57
Block: 1149881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113550 RingCT/type: yes/0
Extra: 01cf9936ae152679e8b6c22bae832e4b9e79418b49c3793d10b23da4af0839dd88021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60fdb7b18df775fb788c488154a2f9548f8cf671d6c6fb5f3ae01670d15e1020 0.600000000000 1635056 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": 1149891, "vin": [ { "gen": { "height": 1149881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60fdb7b18df775fb788c488154a2f9548f8cf671d6c6fb5f3ae01670d15e1020" } } ], "extra": [ 1, 207, 153, 54, 174, 21, 38, 121, 232, 182, 194, 43, 174, 131, 46, 75, 158, 121, 65, 139, 73, 195, 121, 61, 16, 178, 61, 164, 175, 8, 57, 221, 136, 2, 17, 0, 0, 0, 1, 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