Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a10f920dd68759217a86b7bea65b94ed9c790bb1321c45e83ee37a0adf8852cf

Tx prefix hash: 637692970ff6c1eb2ddf17bfa2c3d646f0efe37302efc5df169469f154daf1f6
Tx public key: 6090e1a043fcc9a7a16277c840110326d72e45d8c9c851463b37a739b93505e8
Timestamp: 1702882888 Timestamp [UCT]: 2023-12-18 07:01:28 Age [y:d:h:m:s]: 01:022:23:48:21
Block: 915646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277781 RingCT/type: yes/0
Extra: 016090e1a043fcc9a7a16277c840110326d72e45d8c9c851463b37a739b93505e8021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec4b02c7cc06d859481aaa60f8b07100ed496f792e3c554bb10e88a493cb7f0 0.600000000000 1373042 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": 915656, "vin": [ { "gen": { "height": 915646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec4b02c7cc06d859481aaa60f8b07100ed496f792e3c554bb10e88a493cb7f0" } } ], "extra": [ 1, 96, 144, 225, 160, 67, 252, 201, 167, 161, 98, 119, 200, 64, 17, 3, 38, 215, 46, 69, 216, 201, 200, 81, 70, 59, 55, 167, 57, 185, 53, 5, 232, 2, 17, 0, 0, 0, 1, 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