Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 227f23df50496d3070384fe8c1abf53261c200b2337c7af6b652e3e0a29ee2f0

Tx prefix hash: c04db8b4c8ef70f096268078cbfb625366582c558019e5ed6f6a7d10a7abf47c
Tx public key: 296708445137e4c3a5474d29ab0332821b58d394d941ced70e535dc1aaa4672d
Timestamp: 1718146132 Timestamp [UCT]: 2024-06-11 22:48:52 Age [y:d:h:m:s]: 00:298:23:06:42
Block: 1042189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213632 RingCT/type: yes/0
Extra: 01296708445137e4c3a5474d29ab0332821b58d394d941ced70e535dc1aaa4672d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b951e3b378f960ad9187370f4a0664b515df9d6b9e1638bc4ae36aa8b0af18 0.600000000000 1511048 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": 1042199, "vin": [ { "gen": { "height": 1042189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b951e3b378f960ad9187370f4a0664b515df9d6b9e1638bc4ae36aa8b0af18" } } ], "extra": [ 1, 41, 103, 8, 68, 81, 55, 228, 195, 165, 71, 77, 41, 171, 3, 50, 130, 27, 88, 211, 148, 217, 65, 206, 215, 14, 83, 93, 193, 170, 164, 103, 45, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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