Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c744749650b3b85e61426c8163e13c737a1917d326b3a10420d6ec11d4050712

Tx prefix hash: b4a9782e07c2b6c3e57ebdd42556e909ac3b579feeacd442e226a257838453f7
Tx public key: 857ba84035bc84fd941cc1c10c3f2e630cf504ed4ca9072838e601b8a9b0b67f
Timestamp: 1718406588 Timestamp [UCT]: 2024-06-14 23:09:48 Age [y:d:h:m:s]: 00:170:08:54:32
Block: 1044350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121937 RingCT/type: yes/0
Extra: 01857ba84035bc84fd941cc1c10c3f2e630cf504ed4ca9072838e601b8a9b0b67f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8784aef4d942c43685d1bfa18a4590d890ff7d3ec24d8a852ce58a2caec98231 0.600000000000 1513635 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": 1044360, "vin": [ { "gen": { "height": 1044350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8784aef4d942c43685d1bfa18a4590d890ff7d3ec24d8a852ce58a2caec98231" } } ], "extra": [ 1, 133, 123, 168, 64, 53, 188, 132, 253, 148, 28, 193, 193, 12, 63, 46, 99, 12, 245, 4, 237, 76, 169, 7, 40, 56, 230, 1, 184, 169, 176, 182, 127, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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