Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45c90ef1f0da237406343d37e265cbeb3108edbed5b461a4838be4ca4410a2e6

Tx prefix hash: 173942a315a3b9383751b027d28fcc607a78fc18b6f1cbbef1dd50ce7fdcd670
Tx public key: 0f08b85c540927c365c785dc430431692f3a606b4b9dbd0104a1dae4df01c5db
Timestamp: 1714552027 Timestamp [UCT]: 2024-05-01 08:27:07 Age [y:d:h:m:s]: 00:352:06:29:45
Block: 1012395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251822 RingCT/type: yes/0
Extra: 010f08b85c540927c365c785dc430431692f3a606b4b9dbd0104a1dae4df01c5db0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2daeb12e4c0ad65e970e5d1fdcc4e47e8611834c335e98f447993b26849397a 0.600000000000 1474903 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": 1012405, "vin": [ { "gen": { "height": 1012395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2daeb12e4c0ad65e970e5d1fdcc4e47e8611834c335e98f447993b26849397a" } } ], "extra": [ 1, 15, 8, 184, 92, 84, 9, 39, 195, 101, 199, 133, 220, 67, 4, 49, 105, 47, 58, 96, 107, 75, 157, 189, 1, 4, 161, 218, 228, 223, 1, 197, 219, 2, 17, 0, 0, 0, 4, 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