Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d727c59d888ecabb6be07d90237accccb3f3732bfbc819352141f7f14b5071

Tx prefix hash: 52b3c4c985391ad4c17332cc3c42a2ca0fad75a49b226fb902eb64248dd5181b
Tx public key: c3283af47e79ef0204d2f87d8a53afc168dc51218e06d5fe247534e616e10c27
Timestamp: 1737312398 Timestamp [UCT]: 2025-01-19 18:46:38 Age [y:d:h:m:s]: 00:336:17:55:41
Block: 1200913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238243 RingCT/type: yes/0
Extra: 01c3283af47e79ef0204d2f87d8a53afc168dc51218e06d5fe247534e616e10c2702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a35c59b9944126ba8771a79c040c71c318fd85c2e9f8d03cdd7acb8c081df51 0.600000000000 1687560 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": 1200923, "vin": [ { "gen": { "height": 1200913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a35c59b9944126ba8771a79c040c71c318fd85c2e9f8d03cdd7acb8c081df51" } } ], "extra": [ 1, 195, 40, 58, 244, 126, 121, 239, 2, 4, 210, 248, 125, 138, 83, 175, 193, 104, 220, 81, 33, 142, 6, 213, 254, 36, 117, 52, 230, 22, 225, 12, 39, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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