Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fcca6d5de0858dac2d7954f1bf857c3c0f793c3271b943c5c5f49183cfa5eaa

Tx prefix hash: ddc1415322aa05013f71ade82998ea2595d79969eecb8a1d018cb1d3a6d749f6
Tx public key: 68596cd5cc190aa1000da41f115d62a1350fef909bbe2842a0f6afeb48f1e630
Timestamp: 1702709639 Timestamp [UCT]: 2023-12-16 06:53:59 Age [y:d:h:m:s]: 01:331:12:04:39
Block: 914210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495783 RingCT/type: yes/0
Extra: 0168596cd5cc190aa1000da41f115d62a1350fef909bbe2842a0f6afeb48f1e630021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33cf91e2ed65df5466c3345cd3e27ec94a6e275b6f8d81f5f1520f735430aa4c 0.600000000000 1371496 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": 914220, "vin": [ { "gen": { "height": 914210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33cf91e2ed65df5466c3345cd3e27ec94a6e275b6f8d81f5f1520f735430aa4c" } } ], "extra": [ 1, 104, 89, 108, 213, 204, 25, 10, 161, 0, 13, 164, 31, 17, 93, 98, 161, 53, 15, 239, 144, 155, 190, 40, 66, 160, 246, 175, 235, 72, 241, 230, 48, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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